[sipcore] rfc3261: sip-uri user parameter
Brett Tate <brett@broadsoft.com> Wed, 13 January 2010 22:30 UTC
Return-Path: <brett@broadsoft.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1AA43A67FB for <sipcore@core3.amsl.com>; Wed, 13 Jan 2010 14:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_45=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMR-4g8KTp1r for <sipcore@core3.amsl.com>; Wed, 13 Jan 2010 14:30:08 -0800 (PST)
Received: from smtp-out01.seaservers.net (smtp-out01.seaservers.net [72.37.232.66]) by core3.amsl.com (Postfix) with ESMTP id D6BA23A67F8 for <sipcore@ietf.org>; Wed, 13 Jan 2010 14:30:08 -0800 (PST)
Received: from EXMBXCLUS01.citservers.local ([fe80:0000:0000:0000:a488:d1ec:167.6.58.109]) by casumhub01.citservers.local ([172.16.98.57]) with mapi; Wed, 13 Jan 2010 14:30:06 -0800
From: Brett Tate <brett@broadsoft.com>
To: SIPCORE <sipcore@ietf.org>
Date: Wed, 13 Jan 2010 14:29:41 -0800
Thread-Topic: rfc3261: sip-uri user parameter
Thread-Index: AcqUn+ZpEIdQ4HxwS7Cq66yNz89bag==
Message-ID: <747A6506A991724FB09B129B79D5FEB6145F96714A@EXMBXCLUS01.citservers.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [sipcore] rfc3261: sip-uri user parameter
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2010 22:30:09 -0000
Since we were unable to reach agreement on sip-implementors, I thought that I'd try sip-core. https://lists.cs.columbia.edu/pipermail/sip-implementors/2010-January/024131.html What does adding user=phone to sip-uri mean? 1) Whatever the owner of sip-uri's host wants it to mean; it isn't restricted to being a telephone-subscriber. Thus okay to add user=phone when userinfo portion of sip-uri is "anonymous@", not present, and etcetera. 2) The userinfo portion of sip-uri contains telephone-subscriber (defined within rfc3966/rfc2806). 3) Another meaning. Thanks, Brett
- [sipcore] rfc3261: sip-uri user parameter Brett Tate
- Re: [sipcore] rfc3261: sip-uri user parameter Paul Kyzivat